MOC Go Live Checklist

The steps below provide a generic guidance for going live with the MOC application following the administrator training. Please note that all steps below may not apply in your situation. Use the knowledge gained during the administrator training, along with your specific situation to formulate a plan for going live.

Please note that you do not need to be 100% complete on applicable items below before going live. The application allows you to change a majority of the items without losing any current information. Quite often, simply diving in while the training is fresh in your minds and making sure that you are reasonably complete on steps below offers the most efficient implementation.

  1. Make sure that your MOC site has been set up a trusted site on all your user computers. Also, make sure that the e-mails from the site to your users are not blocked.
  2. Review the imported organization structure (company, division and account) data and make sure that it closely matches your mode of operation, management hierarchy and administration.
  3. Review the imported people data to make sure that everyone that needs to use the MOC application is in the system.
  4. Review to make sure that the people trained have the correct administrative permissions for the live MOC site.
  5. Plan out a directory structure on your LAN to store MOC attachments (drawings, documents, etc.). Make sure that your users have correct access permissions to such files. You can also store and attach files from a SharePoint server or a document management system. There are also custom interfaces available to move files automatically from a user's local drive to a network share or a SharePoint server, and link them as attachments to MOC. Please contact your administrator or Frontline Data Solutions technical support for information on such interfaces.
  6. Create Ref Codes.
  7. Create implementation requirements. Requirements are standard generic MOC implementation tasks, such as Send Notice, Pre-Startup Safety Review (PSSR) checklist, documentation update, etc. These can be attached to online forms or checklists, or could just be simple task names that you would like to assign and track as part of an MOC. If you wish to start out simple, start with a few basic implementation requirements, and add others later as you develop experience with the system.
  8. Create profiles. This is an important step that simplifies creating MOCs and maintains consistency. Again, start with a few basic profiles, and add others later as you develop experience.
  9. Establish a small group of people that you would go live with. With you being the originator of a simple MOC, these people would play the roles of evaluators (optional), collaborators (optional), approvers, implementers and implementation manager. Train these people on how to complete their assigned MOC tasks from their system desktops when they receive e-mails about assigned tasks.
  10. Enter one or two simple MOCs; MOCs that do not contain a lot of evaluation and implementation requirements. Example is a simple process change or a procedure change with a few collaborators, approvers and requirements.
  11. Take the simple MOC through completion. Make sure to include a few people to notify via Send Notice. If all participants complete their assigned tasks, you should get the MOC back on your system desktop to complete (close-out). If the MOC is hung up at approval or implementation stage (you can check this in the in process folder), contact these people.
  12. As you develop more experience with the application, add the following to your MOCs:
    1. Use evaluation stage for risk/benefit and degree of change analysis.
    2. Use collaboration stage.
    3. Create forms for implementation tasks such as Pre-Startup Safety Review (PSSR). We have included some example forms that you can copy and edit. Attach these to the implementation requirements. You can also create a form for an evaluation requirement. For a requirement attached to a form, you can also learn and experiment with automatic and manual action items.
    4. Create/enhance profiles (step 8 above).
    5. Create pre-approvals and place shortcuts to these on users' system desktops. A pre-approval allows any user to submit an MOC request without needing MOC administrator permission. Train users on how to submit MOC requests using shortcuts.
    6. Use the LMS skillsets feature (you can learn about it using LMS help manual; search for skillsets) to create pre-defined groups of people for MOC Send Notice sign-offs. This will make it easier to select large groups of people consistently for MOC notices via such skillsets. This will also better organize MOCs assigned to people for sign-offs.
    7. Add equipment list and attach to your MOCs. We may have already imported this for you if you provided it to us. It is easy to manually add/edit/update an equipment.
    8. Use memo MOCs.
  13. Grant additional people MOC user permission. Train these people on how to create and originate MOCs.
  14. MOC notification e-mail frequency is already configured in the application based on our experience. Please contact your MOC administrator or Frontline Data Solutions if you have a need to change this frequency.